Verify that all-day events can be synchronized when server and device are in the same time zone

Verify that time zone selected on server and mobile device is the same.

Create an all-day event on server on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Synchronize with mobile device.

Event should display as an all-day event in the device calendar on 06/12/06.

If the mobile device uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that all-day events can be synchronized when server and device are in a different time zone

Set the time zone on the server to GMT (London) and the time zone on the mobile device to GMT-5 (Eastern Time, US & Canada)

Create an all-day event on server on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Synchronize with mobile device.

Event should display as an all-day event in the mobile device on 06/12/06.

If the mobile device uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that basic calendar entries synchronize to the device.

From the Server, create a single instance future all-day event, filling out all fields with maximum input, with a reminder.

Perform a synchronization

From the device, modify the day event and remove the reminder.

Perform a synchronization

The day event should display on the device as an all day event with all fields on the server correctly mapped to corresponding fields on the device. The reminder should also be set on the device.

After making modifications and synchronizing, the changes should display on the server as well. Any client side truncation of fields should not be propagated back to the server.

BOF Topic: What form should the iCalendar be to represent a day event? Currently the vCalendar to send depends greatly on the manufacturer of the device.

Verify that anniversaries can be synchronized

Create an anniversary on the server on 4^th May 2007

Perform a synchronization

The anniversary should display on the device on 4^th May 2007

Verify boundary conditions

Create an all-day event/anniversary on 31^st March 2007 and 31^st December 2007

The all-day event/anniversary should display on the device on 31/03/2007 and 31/12/2007

Verify that basic calendar entries synchronize to the device.

Perform previous test cases, but for Holidays instead of All Day Events

A ‘Holiday’ is a special type of all-day event supported by some calendar products

Holidays may not be supported in the same fashion for all systems.

The Holiday should display on the device as something appropriate (as a holiday or an all day event depending on what the device can support) with all fields on the server correctly mapped to corresponding fields on the device.

On the ensuing synchronization changes should not be propagated to the server as holidays can’t be changed.

BOF Topic: What should be expected behaviour? Should a modify be sent back to the device to put the holiday back? Some systems would allow the holiday to be removed. How do you specify that something is a holiday in iCalendar?

Verify that all-day event modifications can be synchronized correctly

Verify that time zone selected on server and mobile device is the same.

Create an all-day event on server on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Perform a synchronization

Update all-day event on server and modify subject to ‘all-day event modified’.

Perform a synchronization

Event title on device calendar should be modified to ‘all-day event modified’ and remain an (untimed) all-day event.

If the device calendar application uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that all-day event modifications can be synchronized correctly

Set the time zone on the server to GMT (London) and the time zone on the mobile device to GMT-5 (Eastern Time, US & Canada).

Create an all-day event on server on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Perform a synchronization

Update all-day event on server and modify subject to ‘all-day event modified’.

Perform a synchronization

Event title on device calendar should be modified to ‘all-day event modified’ and remain an (untimed) all-day event.

If the device calendar application uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that basic calendar entries synchronize to the device.

For multi-day Day Events, please read Appendix A before testing.

From the Server, create a single instance Day Event that starts tomorrow and ends 3 days later. Make sure this does not span outside your synchronization range.

Perform a synchronization

From the device, modify the end date to end 1 day earlier than the previous end date (If the device supports multi-day Day Events)

Perform a synchronization

For devices that support multi-day Day Events, the entry should display on the device with a Day Event that spans for the 4 days, as it is on the server.

For devices that do not support multi-day Day Events results may vary.

After modifying the end date from the device and synchronizing, the entry on the server should be one day shorter, reflecting the change made on the device.

BOF Topic: What should be expected behaviour? What should iCalendar look like?

Verify that a basic deletion synchronize to the device.

From the Server, delete a single instance meeting, day event, and holiday

Perform a synchronization

All the selected entries are removed from the device. This should not affect any of the other existing entries.

Verify that basic calendar entries can be synchronized to the server

Verify that time zone selected on server and mobile device is the same.

Create an all-day event on the mobile device on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Perform a synchronization

Event should display on the server as an all-day event on 06/12/06.

If the server calendar application uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that basic calendar entries can be synchronized to the server

Set the time zone on the server to GMT (London) and the time zone on the mobile device to GMT-5 (Eastern Time, US & Canada).

Create an all-day event on the mobile device on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Perform a synchronization

Event should display on the server as an all-day event on 06/12/06.

If the server calendar application uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that basic calendar entries can be synchronized to the server

On the device, create a single instance future all-day event, filling out all fields with maximum input, with a reminder.

Perform a synchronization

From the device, modify the day event and remove the reminder.

Perform a synchronization

The day event should display on the server as an all day event with all fields on the server correctly mapped to corresponding fields on the device. The reminder should also be set on the server.

After making modifications and synchronizing, the changes should display on the server as well. Any client side truncation of fields should not be propagated back to the server.

BOF Topic: What form should the iCalendar be to represent a day event?

Verify that anniversaries can be synchronized

Create an anniversary on the device on 4^th May 2007

Perform a synchronization

The anniversary should display on the server on 4^th May 2007

Verify that all-day event modifications can be synchronized correctly

Verify that time zone selected on server and mobile device is the same.

Create an all-day event on server on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’.

Synchronize with mobile device.

Update all-day event on mobile device and modify subject to ‘all-day event modified’.

Synchronize with server.

Event subject should be modified to ‘all-day event modified’ and remain an (untimed) all-day event.

If the server calendar application uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that all-day event modifications can be synchronized correctly

Set the time zone on the server to GMT (London) and the time zone on the mobile device to GMT-5 (Eastern Time, US & Canada). Create an all-day event on server on 6^th December 2006 (start date 06/12/06, end date 06/12/06) with a subject of ‘all-day event’. Synchronize with mobile device.

Update all-day event on mobile device and modify subject to ‘all-day event modified’. Synchronize with server.

Event subject should be modified to ‘all-day event modified’ and remain an (untimed) all-day event.

If the server calendar application uses an icon to distinguish an all-day event from a timed appointment this is displayed for this entry.

Verify that basic calendar entries can be synchronized to the server

For multi-day Day Events, please read section in Appendix A before testing.

If the device allows for creation of multi-day Day Events, then create a single instance Day Event that starts tomorrow and ends 3 days later. Make sure this does not span outside your synchronization range.

Perform a synchronization

From the device, modify the end date to end 1 day earlier than the previous end date.

Perform a synchronization

Upon the first synchronization, the multi-day Day Event should display on the Server spanning 4 days.

After modifying the entry and synchronizing, the server side entry should display as being one day less.

Verify that a basic deletion synchronize to the server.

From the device, delete a single instance meeting, day event, and holiday

Perform a synchronization

All the selected entries are removed from the server. This should not affect any of the other existing entries.